Systems, methods, and storage media for pre-approving onboarding to a payment platform

ABSTRACT

Systems, methods, and storage media for pre-approving onboarding to a payment platform, executing on a processing device are disclosed. Exemplary implementations may: access a node network; determine a first business entity associated with a first node of the plurality of nodes is not a member of a payment platform; determine a total strength of connections of the first node to one or more nodes of the plurality of nodes exceeds a predetermined threshold value; and flag the first node of the plurality of nodes for an offer of onboarding to the payment platform consequent to determining the total strength of connections of the first node to the one or more nodes of the plurality of nodes exceeds the predetermined threshold value.

BACKGROUND

The proliferation of the internet has fundamentally changed variousaspects of individuals' lives, such as communication, work, education,finance, social and personal relationships, etc. For example, theinternet has remarkably increased the amount of information availableand decreased the transaction cost of obtaining such information. It hasalso enabled new ways to analyze information available to provideplatforms to make interactions between entities faster and easier.

SUMMARY

One aspect of the present disclosure relates to a system configured forpre-approving onboarding to a payment platform, executing on aprocessing device. The system may include one or more hardwareprocessors configured by machine-readable instructions. The processor(s)may be configured to access a node network. A plurality of nodes of thenode network may include data associated with a plurality of businessentities. Strength of connections between nodes may be weightedaccording to a number of transactions between the respective associatedbusiness entities. The processor(s) may be configured to determine afirst business entity associated with a first node of the plurality ofnodes is not a member of a payment platform. The processor(s) may beconfigured to determine a total strength of connections of the firstnode to one or more nodes of the plurality of nodes exceeds apredetermined threshold value. The processor(s) may be configured toflag the first node of the plurality of nodes for an offer of onboardingto the payment platform consequent to determining the total strength ofconnections of the first node to the one or more nodes of the pluralityof nodes exceeds the predetermined threshold value.

Another aspect of the present disclosure relates to a method forpre-approving onboarding to a payment platform, executing on aprocessing device. The method may include accessing a node network. Aplurality of nodes of the node network may include data associated witha plurality of business entities. Strength of connections between nodesmay be weighted according to a number of transactions between therespective associated business entities. The method may includedetermining a first business entity associated with a first node of theplurality of nodes is not a member of a payment platform. The method mayinclude determining a total strength of connections of the first node toone or more nodes of the plurality of nodes exceeds a predeterminedthreshold value. The respective associated business entities of the oneor more nodes may be not a member of the payment platform. The methodmay include flagging the first node of the plurality of nodes for anoffer of onboarding to the payment platform consequent to determiningthe total strength of connections of the first node to the one or morenodes of the plurality of nodes exceeds the predetermined thresholdvalue.

Yet another aspect of the present disclosure relates to a non-transientcomputer-readable storage medium having instructions embodied thereon,the instructions being executable by one or more processors to performany of the method components above for pre-approving onboarding to apayment platform. These and other features, and characteristics of thepresent technology, as well as the methods of operation and functions ofthe related elements of structure and the combination of parts andeconomies of manufacture, will become more apparent upon considerationof the following description and the appended claims with reference tothe accompanying drawings, all of which form a part of thisspecification, wherein like reference numerals designate correspondingparts in the various figures. It is to be expressly understood, however,that the drawings are for the purpose of illustration and descriptiononly and are not intended as a definition of the limits of theinvention. As used in the specification and in the claims, the singularform of “a”, “an”, and “the” include plural referents unless the contextclearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured for pre-approving onboarding to apayment platform, in accordance with one or more implementations.

FIG. 2 illustrates a method for selection of entities for an onboardingoffer in accordance with one or more implementations.

FIG. 3 illustrates a method for pre-approving onboarding to a paymentplatform in accordance with one or more implementations.

FIG. 4 illustrates a graphical user interface illustrating dynamic logosin accordance with one or more implementations.

DETAILED DESCRIPTION

Aspects of the disclosure relate to onboarding and authenticating buyersand sellers to a platform. The platform may handle payments and feetransactions between buyers and sellers that are participating in theplatform. In some implementations, handling payments and/or feetransactions by the platform comprises the platform using existingpayment tools that may otherwise also be accessible outside theplatform. The existing payment tools may have already been used forpayments between the respective entities prior to onboarding and/orauthenticating of one or more of the respective entities to theplatform. The buyers and sellers may be business of various sizes (e.g.,sole proprietors, independent contractors, small businesses, mediumbusinesses, large businesses, etc.). Help with onboarding andauthenticating may include automatic performing of underwriting wherenecessary, pre-approved onboarding, and enticements for buyers andsellers to join the platform. In some implementations, a node network ofbusinesses and their interconnections is maintained to provide data forfaster onboarding and identification of businesses for which toconfigure offers for onboarding.

In some implementations, onboarding and authenticating business entitiesto a platform comprises accessing a node network. The node network maycomprise individual nodes, each associated with an entity (e.g., abusiness entity) where information is gathered and analyzed about howthe entities associated with the nodes are interacting and strength ofrelationship between entities. In some implementations, one or moreconnections between nodes indicate a relationship between entities. Asubset of entities with nodes in the node network may be participatingin the platform. Connections between nodes may be indicative of types oftransactions, a number of transactions, frequency of transactions, otherconnections between the entities, and the like. In some implementations,the connections between two or more nodes are analyzed to determine if aparticular entity may be receptive to an onboarding offer or an offer tolearn more about the benefits of a function or feature of the platform.Access to the platform can increase the speed, reliability, costeffectiveness, convenience, and the like of transactions betweenentities that are part of the platform. In some implementations,information analyzed through transaction history is used to preapprove afunctionality available on the platform to include in an offer to jointhe platform. In some implementations, information analyzed throughconnections in the node network is used to preapprove a functionalityavailable on the platform to include in an offer to join the platform.In some implementations, information analyzed through connections in thenode network (e.g., transaction activity between two nodes) is used togenerate one or more specific benefits of joining the platform or one ormore projected savings upon joining the platform.

In some implementations, a node network comprising nodes associated withentities (e.g., business) is built up for use by the platform. The nodenetwork connection information may be analyzed to predict entitiesreceptive to an onboarding offer to a platform comprising functionalityto handle payments and fees between entities. In some implementations,handling payments by the platform comprises the platform using existingpayment tools that may be accessible outside the platform. The existingpayment tools may have already been used for payments between therespective entities.

In some implementations, a solution to a technical problem of using acomputing device and a node network comprising connections to entitiesto predict receptibility to an offer to join a platform comprisesidentifying transactions between buying entities and selling entitiesand using the transactions to create or update connections between nodesof the node network. In some implementations, connections are created orupdated automatically between nodes of the node network through analysisof transaction data. Analysis of transaction data may also be used toidentify an entity for the creation of a new node of the node network.Feedback may be used to correct incorrect connections, update weightvalues of connections, and prevent incorrect connections based onsimilar names of entities. Additional information may be used to help inthe correct creation or updating of connections, e.g., data from publicdatabases, volunteered data, available geographical locationinformation, and the like.

In some implementations, a solution to a technical problem of using acomputing device to pre-approve and/or activate functionality associatedwith an onboarding offer to a platform comprises predicting entitiesthat may be receptive to an offer based on a node network and sendingthe offer with information on the pre-approved or activatedfunctionality. In some implementations, the offer may direct a user of acomputing device associated with the entity to a landing page, website,application, etc. to communicate the offer and receive acceptance of theoffer. Logos and other visuals associated with entities to which theofferee already has connections to that are already on the platform maybe displayed. In some implementations, size, color, prominence on thescreen, and other visual indications may be adjusted to represent astrength of a connection between the respective entity and the offeree.Visuals/logos show all the businesses connected to the potentialcustomer that are already on the platform (from Node Network data). Insome implementations pre-approved or activated functionality based onanalysis of available transaction data (e.g., transaction data stored inthe node network data) is used to immediately give access to thepre-approved or activated functionality upon acceptance of the offer(e.g., one-click onboarding). Transaction data may also be used toensure identification of the entity with sufficient probability ofaccuracy. In some implementations, other sources of information are alsoused for verification, including available third-party information(e.g., articles of incorporation), analyzed invoices from transactionsbetween entities. In some implementations, information from the analyzeddata is used to fill in missing data needed in the onboarding process.

In some implementations, a solution to a technical problem of visuallyrepresenting connections between entities of a node network comprisesdisplaying Logos and other visuals associated with entities connected inthe node network. In some implementations, size, color, prominence onthe screen, and other visual indications may be adjusted to represent astrength of a connection between two nodes of the node network.Visuals/logos may show all entities connected to a respective entity inthe node network that are already on a platform.

FIG. 1 illustrates a system 100 configured for pre-approving onboardingto a payment platform, executing on a processing device, in accordancewith one or more implementations. In some implementations, system 100may include one or more servers 102. Server(s) 102 may be configured tocommunicate with one or more client computing platforms 104 according toa client/server architecture and/or other architectures. Clientcomputing platform(s) 104 may be configured to communicate with otherclient computing platforms via server(s) 102 and/or according to apeer-to-peer architecture and/or other architectures. Users may accesssystem 100 via client computing platform(s) 104.

Server(s) 102 may be configured by machine-readable instructions 106.Machine-readable instructions 106 may include one or more instructioncircuits. The instruction circuits may include computer programcircuits. The instruction circuits may include one or more of a networkinterface circuit 112, an offer circuit 114, a transaction historyanalysis circuit 116, an onboarding circuit 118, an account circuit 120,and/or other instruction circuits.

Network interface circuit 112 may be configured such that data passingthrough the network interface circuits 112 can be encrypted such thatthe network interface circuit 112 is a secure communication module. Thenetwork 105 enables components of the system 100 to communicate witheach other (e.g., the server(s) 102). The network 105 is a data exchangemedium, which may include wireless networks (e.g., cellular networks,Bluetooth®, WiFi, Zigbee®, etc.), wired networks (e.g., Ethernet, DSL,cable, fiber-based, etc.), or a combination thereof. In someembodiments, the network 105 includes the internet.

Offer circuit 114 may be configured to determine an entity to send anoffer. In some implementations offer circuit 114 is configured to accessa node network 109. A plurality of nodes of the node network 109 mayinclude data associated with a plurality of entities (e.g., soleproprietors, independent contractors, small businesses, mediumbusinesses, large businesses, etc.). Strength of connections betweennodes may be weighted according to a number of transactions between therespective associated entities. In some implementations, offer circuit114 is configured to determine an entity does not have an associatednode in the node network. The entity may be identified by analyzingtransaction history between the entity and one or more entities withcorresponding nodes in the node network 109. Offer circuit 114 may beconfigured to determine a first entity that is associated with a firstnode of a plurality of nodes is not a member of a platform (e.g., apayment platform). In some implementations, the offer circuit 114 isconfigured to determine that a total strength of connections of thefirst node to one or more nodes of the plurality of nodes exceeds apredetermined threshold value. The respective entities associated withthe one or more nodes may already be on or using the payment platform.In some implementations offer circuit 114 is configured to flag thefirst node of the plurality of nodes for an offer of onboarding to thepayment platform consequent to determining that the total strength ofconnections of the first node to the one or more nodes of the pluralityof nodes exceeds the predetermined threshold value. The offer mayinclude data including a strength of connections between the firstentity and the plurality of entities. In some implementations the offercircuit 114 is configured to determine a data field associated with apre-approval of onboarding to the payment platform of the first entityis incomplete. Data to complete the data field may be obtained fromtransaction history analysis circuit 116. In some implementations offercircuit 114 is configured to select a parameter for inclusion in anoffer. The parameter may be associated with a functionality of thepayment platform. In some implementations, joining an entity to theplatform may include creating an account on the payment platform, aconfiguration of the created account based on including thefunctionality of the payment platform in the offer. Selection of thefirst parameter may be based on analyzing the transaction history usingtransaction history analysis circuit 116. In some implementations, theoffer circuit 114 is configured to send the offer to a device associatedwith the entity (e.g., a client computing platform 104). In someimplementations, the offer circuit 114 is configured to receive anacceptance to the offer from the device associated with the entity(e.g., a client computing platform 104).

Transaction history analysis circuit 116 may be configured to analyze atransaction history associated with an entity. In some implementations,transaction history analysis circuit 116 is configured to analyze atransaction history between two or more entities associated with nodesin a node network 109. The transaction history analysis circuit 116 maybe configured to determine types of transactions, total number oftransactions, frequency of transactions, and the like between the two ormore entities. In some implementations, the transaction history isobtained from a different source than the node network 109. In someimplementations, the transaction history analysis circuit 116 isconfigured to analyze transaction history for data that can be used in adata field that is required for an offer to send to an entity. The datafield may also be a data field required for onboarding the entity to aplatform (e.g., a payment platform). Analyzing the transaction historymay include determining a value of a parameter associated with thetransaction history exceeds a predetermined threshold value. In someimplementations, the transaction history analysis circuit 116 may beconfigured to determine types of transactions, total number oftransactions, frequency of transactions, and the like between two ormore entities that have connections to a common entity. In someimplementations, the transaction history analysis circuit 116 isconfigured to use analytics to determine a more efficient flow oftransactions in a speculative configuration where an entity has joinedthe platform. In some implementations, the transaction history analysiscircuit 116 is configured to analyze transaction history to determinepossible incentives to offer an entity to join the platform. Incentivesmay include discounts, fee structures, payment methods, payment terms,underwriting of transactions, and the like. In some implementations,transaction history may be stored using a private permissionedblockchain based distributed network. Transaction volume may be analyzedand compared to other members of the platform to determine platformmembers have transactions with mutual entities that are not on theplatform. This analysis may be done by accessing common shared databeing written to the blockchain.

Onboarding circuit 118 may be configured to add an entity to theplatform (e.g., a payment platform). This may be based on receiving theacceptance to the offer. In some implementations, the onboarding circuit118 is configured to add an entity to the platform further based onpreapproving a functionality of the platform. Further functionality mayalso be identified even after an entity has been added to the platformif another functionality or plurality of functionalities is preapprovedto the entity subsequent to adding the entity to the platform. In someimplementations, the onboarding circuit 118 is configured to send arequest for data associated with the additional functionality to thedevice associated with the entity. In some implementations, theonboarding circuit 118 is configured to receive the data from the deviceassociated with the entity responsive to the request.

Account circuit 120 may be configured to update a node network 109 withaccount related information. In some implementations, the accountcircuit 120 is configured to receive data including a first transactioninformation between a first entity and a second entity. The accountcircuit 120 may be configured to receive data including a secondtransaction with the second entity. In some implementations, the accountcircuit 120 generates data including the strength of connections betweenthe first entity and the second entity (or any respective entityassociated with a node in a node network 109) wherein the data mayinclude graphical data that, when displayed on a computing device (e.g.,a client computing platform 104) associated with the first businessentity, illustrates the strength of the connections between the firstentity and the second entity. In some implementations account circuit120 is configured to update an account of the platform to add anadditional functionality. Updating a node network 109 may includecreating a new node in the node network associated with a new entity(e.g., a business entity). Updating a node network 109 may includeupdating a weight of a connection between a first entity and a secondentity. The weight of the connection may be updated consequent toreceiving data including a transaction between the first entity and thesecond entity.

In some implementations, server(s) 102, client computing platform(s)104, and/or external resources 106 may be operatively linked via one ormore electronic communication links. For example, such electroniccommunication links may be established, at least in part, via a network105 such as the Internet and/or other networks. It will be appreciatedthat this is not intended to be limiting, and that the scope of thisdisclosure includes implementations in which server(s) 102, clientcomputing platform(s) 104, and/or external resources 106 may beoperatively linked via some other communication media.

A given client computing platform 104 may include one or more processorsconfigured to execute computer program circuits. The computer programcircuits may be configured to enable an expert or user associated withthe given client computing platform 104 to interface with system 100and/or external resources 106, and/or provide other functionalityattributed herein to client computing platform(s) 104. By way ofnon-limiting example, the given client computing platform 104 mayinclude one or more of a desktop computer, a laptop computer, a handheldcomputer, a tablet computing platform, a NetBook, a Smartphone, a gamingconsole, and/or other computing platforms.

External resources 106 may include sources of information outside ofsystem 100, external entities participating with system 100, and/orother resources. In some implementations, some or all of thefunctionality attributed herein to external resources 106 may beprovided by resources included in system 100.

Server(s) 102 may include electronic storage 108, one or more processors110, and/or other components. Server(s) 102 may include communicationlines, or ports to enable the exchange of information with a networkand/or other computing platforms. Illustration of server(s) 102 in FIG.1 is not intended to be limiting. Server(s) 102 may include a pluralityof hardware, software, and/or firmware components operating together toprovide the functionality attributed herein to server(s) 102. Forexample, server(s) 102 may be implemented by a cloud of computingplatforms operating together as server(s) 102.

Electronic storage 108 may comprise non-transitory storage media thatelectronically stores information. The electronic storage media ofelectronic storage 108 may include one or both of system storage that isprovided integrally (i.e., substantially non-removable) with server(s)102 and/or removable storage that is removably connectable to server(s)102 via, for example, a port (e.g., a USB port, a firewire port, etc.)or a drive (e.g., a disk drive, etc.). Electronic storage 108 mayinclude one or more of optically readable storage media (e.g., opticaldisks, etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 108 may include one or more virtual storageresources (e.g., cloud storage, a virtual private network, and/or othervirtual storage resources). Electronic storage 108 may store softwarealgorithms, information determined by processor(s) 110, informationreceived from server(s) 102, information received from client computingplatform(s) 104, and/or other information that enables server(s) 102 tofunction as described herein.

Processor(s) 110 may be configured to provide information processingcapabilities in server(s) 102. As such, processor(s) 110 may include oneor more of a digital processor, an analog processor, a digital circuitdesigned to process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information. Although processor(s) 110 is shown in FIG. 1 asa single entity, this is for illustrative purposes only. In someimplementations, processor(s) 110 may include a plurality of processingunits. These processing units may be physically located within the samedevice, or processor(s) 110 may represent processing functionality of aplurality of devices operating in coordination. Processor(s) 110 may beconfigured to execute circuits 112, 114, 116, 118, 120 and/or othercircuits. Processor(s) 110 may be configured to execute circuits 112,114, 116, 118, 120 and/or other circuits by software; hardware;firmware; some combination of software, hardware, and/or firmware;and/or other mechanisms for configuring processing capabilities onprocessor(s) 110. As used herein, the term “circuit” may refer to anycomponent or set of components that perform the functionality attributedto the circuit. This may include one or more physical processors duringexecution of processor readable instructions, the processor readableinstructions, circuitry, hardware, storage media, or any othercomponents.

It should be appreciated that although circuits 112, 114, 116, 118, 120,and are illustrated in FIG. 1 as being implemented within a singleprocessing unit, in implementations in which processor(s) 110 includesmultiple processing units, one or more of circuits 112, 114, 116, 118,120, and/or may be implemented remotely from the other circuits. Thedescription of the functionality provided by the different circuits 112,114, 116, 118, 120, and/or described below is for illustrative purposes,and is not intended to be limiting, as any of circuits 112, 114, 116,118, 120, and/or may provide more or less functionality than isdescribed. For example, one or more of circuits 112, 114, 116, 118, 120,and/or may be eliminated, and some or all of its functionality may beprovided by other ones of circuits 112, 114, 116, 118, and/or 120. Asanother example, processor(s) 110 may be configured to execute one ormore additional circuits that may perform some or all of thefunctionality attributed below to one of circuits 112, 114, 116, 118,and/or 120.

FIG. 2 illustrates a method 200 for method for selection of entities foran onboarding offer in accordance with one or more implementations. Theoperations of method 200 presented below are intended to beillustrative. In some implementations, method 200 may be accomplishedwith one or more additional operations not described, and/or without oneor more of the operations discussed. Additionally, the order in whichthe operations of method 200 are illustrated in FIG. 2 and describedbelow is not intended to be limiting.

In some implementations, method 200 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 200 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 200. In brief,method 200 may comprise analyzing transactions, adding or updatingnodes, and building a node network. Method 200 may further compriseaccessing the node network to determine if a first entity (e.g., abusiness entity) that is associated with a first node of a plurality ofnodes is not a member of a payment platform, determine a total strengthof connection of the first node to one or more nodes of the plurality ofnodes exceeds a predetermined threshold value, and flag the first nodeof the plurality of nodes for an offer of onboarding to the paymentplatform.

An operation 202 may include analyzing transactions. In someimplementations, this is an ongoing process for construction andupdating of a node network. A plurality of nodes of the node network mayinclude data associated with a plurality of entities (e.g., businessentities). Analyzing transactions may comprise receiving transactioninformation between two or more of the plurality of entities anddetermining a type of the transaction, total number of transactions,frequency of transactions, and the like between two or more of theplurality of entities. In some implementations, the data about thetransactions is obtained from a third party source (e.g., externalresources 106). In some implementations, analyzing transactions maycomprise receiving transaction information where one or both of theentities are not among the plurality of entities associated with theplurality of nodes of the node network. In some implementations,analyzing transactions may comprise receiving transaction informationwhere there is at least one entity among the plurality of entitiesassociated with the plurality of nodes of the node network and at leastone entity not among the plurality of entities associated with theplurality of nodes of the node network. In some implementations,transaction history is analyzed by searching for recurring and/orpredictable payments or currency transfers. The transaction history maybe obtained from existing payment tools being utilized for paymentbetween respective entities. In some implementations, a probability iscalculated for ability to make future payments based on recurringfinancial transactions. In some implementations, the transaction historyis analyzed for a predicted fee, rate increase, loss in status, reducedcredit rating, reduced opportunity or qualification for offers, and thelike. This can be compared against functionality of the platform thatcan eliminate or mitigate these or similar problems. In someimplementations, transaction history is continually analyzed for one ormore entities associated with nodes in the node network 109. In someimplementations, transaction history is analyzed at a recurringpredetermined time (e.g., a day, a week, etc.) or at predeterminedintervals before analyzing any new transactions with a respectiveentity. In some implementations, analyzing new transactions compriseswaiting for a predetermined time or time lapse and also waiting for atriggering event, such as a new transaction associated with an entity.

An operation 204 may include adding or updating a node of the nodenetwork. accessing a node network. A plurality of nodes of the nodenetwork may include data associated with a plurality of entities. When anew entity is identified through analysis of transaction information, anew node of the node network may be created. Strength of connectionsbetween nodes may be weighted according to a number of transactionsbetween the respective associated business entities. In someimplementations, connections are instead or also weighted based on atype of the transaction, overall total number of transactions, number oftransactions within a particular time period (e.g., a window of mostrecent transactions), frequency of transactions, and the like.

An operation 206 may include building a node network. A plurality ofnodes of the node network may include data associated with a pluralityof business entities. In some implementations, building a node networkassociated with entities (e.g., business entities) comprises identifyinga new entity. Identification of a new entity may be accomplished throughanalysis of transaction information, receipt of a request to add a newentity, receipt of third party data identifying transaction associatedwith a new entity, and the like. In some implementations, building anode network associated with entities comprises updating a connectionbetween two or more existing entities in a node network. Strength ofconnections between nodes may be weighted according to a number oftransactions between the respective associated business entities. Insome implementations, connections are instead or also weighted based ona type of the transaction, overall total number of transactions, numberof transactions within a particular time period (e.g., a window of mostrecent transactions), frequency of transactions, and the like.

An operation 208 may include accessing a node network. A plurality ofnodes of the node network may include data associated with a pluralityof entities (e.g., business entities). Strength of connections betweennodes may be weighted according to a number of transactions between therespective associated business entities. In some implementations,connections between nodes indicate a relationship between entities. Asubset of entities with nodes in the node network may be participatingin a platform (e.g., a payment platform). Connections between nodes maybe indicative of types of transactions, a number of transactions,frequency of transactions, other connections between the entities, andthe like. In some implementations, the connections between two or morenodes are analyzed to determine if a particular entity may be receptiveto an onboarding offer or an offer to learn more about the benefits of afunction or feature of the platform. Access to the platform can increasethe speed, reliability, cost effectiveness, convenience, and the like oftransactions between entities that are part of the platform. In someimplementations, information analyzed through transaction history isused to preapprove a functionality available on the platform to includein an offer to join the platform. The transaction history may beobtained from existing payment tools being utilized for payment betweenrespective entities. In some implementations, information analyzedthrough connections in the node network is used to preapprove afunctionality available on the platform to include in an offer to jointhe platform.

An operation 210 may include determining a first business entityassociated with a first node of the plurality of nodes is not a memberof a payment platform. In some implementations, data is stored in arespective node of the node network associated with the first businessentity indicative of membership of a platform. In some implementations,data is accessed from a respective node of the node network andreferenced with other data (e.g., platform membership database data) todetermine if the first business entity is already a member of theplatform.

An operation 212 may include determining a total strength of connectionsof the first node to one or more nodes of the plurality of nodes exceedsa predetermined threshold value. The respective associated businessentities of the one or more nodes may not be a member of the paymentplatform. In some implementations, a strength of connection may bedetermined by a number of transactions, type of transaction, frequency,recurrence, and the like. Strength of connections may also be weightedaccording to a number of transactions between the respective associatedentities, a type of the transaction, total number of transactions,frequency of transactions, and the like. In some implementations, theremay be more than one connection between nodes. More than one connectionsmay in some implementations be one or more of type of transaction,direction of transaction, size of transaction, and other ways tosub-divide transactions.

An operation 214 may include flagging the first node of the plurality ofnodes for an offer of onboarding to the payment platform consequent todetermining the total strength of connections of the first node to theone or more nodes of the plurality of nodes exceeds the predeterminedthreshold value. In some implementations, flagging the first node of theplurality of nodes requires a further determination of whether theentity associated with the first node is a non-brick-and-mortar vendoror store and associated risks. In some implementations, flagging thefirst node of the plurality of nodes requires a threshold level ofprediction that an entity associated with the first node would bereceptive to offer of onboarding. The prediction level may be based onan analysis of transaction history, an analysis of a number ofconnections between the first node and one or more of the plurality ofnodes already a member of the platform reaching a threshold level, ananalysis of a strength of a connection between the first node and one ormore of the plurality of nodes already a member of the platform reachinga threshold level or levels, a combination of these factors, and thelike. The transaction history may be obtained from existing paymenttools being utilized for payment between respective entities.

In some implementations, flagged entities may be directed to a landingpage, website, application, or sent an offer. In some implementations,the sent offer, landing page, website or landing page uses a userinterface to illustrate the connection of the flagged entity to one ormore entities that are already members of the platform. A visualindication may be logos or other identifiable visuals related to the oneor more entities. In some implementations, the logos or otheridentifiable visuals may be adjusted regarding size, color, prominenceon the screen, and other visual indications to represent a strength of aconnection between the respective entity and the one or more entitiesthat are already members of the platform. Other visuals may be displayedindicating advantages and incentives to joining the platform. In someimplementations visuals indicating advantages and incentives to joiningthe platform may indicate which connections to the one or more entitiesthat are already members of the platform would benefit.

FIG. 3 illustrates a method 300 for pre-approving onboarding to apayment platform in accordance with one or more implementations. Theoperations of method 300 presented below are intended to beillustrative. In some implementations, method 300 may be accomplishedwith one or more additional operations not described, and/or without oneor more of the operations discussed. Additionally, the order in whichthe operations of method 300 are illustrated in FIG. 3 and describedbelow is not intended to be limiting. In some implementations, method300 may be implemented in one or more processing devices (e.g., adigital processor, an analog processor, a digital circuit designed toprocess information, an analog circuit designed to process information,a state machine, and/or other mechanisms for electronically processinginformation). The one or more processing devices may include one or moredevices executing some or all of the operations of method 300 inresponse to instructions stored electronically on an electronic storagemedium. The one or more processing devices may include one or moredevices configured through hardware, firmware, and/or software to bespecifically designed for execution of one or more of the operations ofmethod 300. In brief, method 300 may comprise selecting a parameter forinclusion in an offer, preapproving functionality of a payment platformbased on analyzing transaction history, including the functionality ofthe payment platform in the offer, and sending the offer to a deviceassociated with an entity.

An operation 302 may include selecting a first parameter for inclusionin an offer. The first parameter may be associated with a firstfunctionality of a payment platform. Selection of the first parametermay be based on analyzing a transaction history. In someimplementations, the parameter is based on a value associated with anincentive. Incentives may include discounts, fee structures, paymentmethods, payment terms, underwriting of transactions, and the like.

An operation 304 may include preapproving the first functionality of thepayment platform based on analyzing the transaction history. In someimplementations, the first functionality provides the ability to executean incentive of an offer. The incentive may be driven by a parameterincluded in the offer. Selection of the first parameter may be based onanalyzing a transaction history. In some implementations, the parameteris based on a value associated with an incentive. Incentives may includediscounts, fee structures, payment methods, payment terms, underwritingof transactions, and the like. Analyzing the transaction history mayinclude determining a value associated with the transaction historyexceeds a predetermined threshold value. Analyzing the transactionhistory may include determining types of transactions, total number oftransactions, frequency of transactions, and the like between theofferee entity and one or more entities that are members of theplatform. Analyzing the transaction history may include determiningtypes of transactions, total number of transactions, frequency oftransactions, and the like between two or more entities that haveconnections to a common entity, wherein the offeree entity can be thecommon entity of the two or more entities that have connections to adifferent comment entity. In some implementations, the incentive iscalculated to result in a more efficient flow of transactions in aspeculative configuration where the offeree entity is assumed to havejoined the platform. Incentives may include discounts, fee structures,payment methods, payment terms, push-to-card, reduced costs for entitiesthat are historically cash-based, underwriting of transactions, and thelike.

An operation 306 may include including the first functionality of thepayment platform in the offer based on preapproving the firstfunctionality of the payment platform. In some implementations, theoffer is generated as a landing page, website, application, or the like.In some implementations, the landing page, website or application uses auser interface to illustrate the connection of the flagged entity to oneor more entities that are already members of the platform. A visualindication may be logos or other identifiable visuals related to the oneor more entities. In some implementations, the logos or otheridentifiable visuals may be adjusted regarding size, color, prominenceon the screen, and other visual indications to represent a strength of aconnection between the respective entity and the one or more entitiesthat are already members of the platform. Other visuals may be displayedindicating at least the first functionality as an incentive to join theprogram. In some implementations visuals indicating the firstfunctionality may indicate which connections to the one or more entitiesthat are already members of the platform will be benefited by the firstfunctionality. In some implementations, the offer comprises an interfacefor one-click on-boarding or similar equivalent, where the firstfunctionality has been pre-approved and/or activated and only anacceptance is required.

An operation 308 may include sending the offer to a device associatedwith a first business entity. In some implementations, the offer as sentcomprises a landing page, website, application, or the like. In someimplementations, the landing page, website or application uses a userinterface to illustrate the connection of the flagged entity to one ormore entities that are already members of the platform. A visualindication may be logos or other identifiable visuals related to the oneor more entities. In some implementations, the logos or otheridentifiable visuals may be adjusted regarding size, color, prominenceon the screen, and other visual indications to represent a strength of aconnection between the respective entity and the one or more entitiesthat are already members of the platform. Other visuals may be displayedindicating at least the first functionality as an incentive to join theprogram. In some implementations visuals indicating the firstfunctionality may indicate which connections to the one or more entitiesthat are already members of the platform will be benefited by the firstfunctionality. In some implementations, the offer comprises an interfacefor one-click on-boarding or similar equivalent, where the firstfunctionality has been pre-approved and/or activated and only anacceptance is required.

Referring now to FIG. 4, an interface 400 on a display of an exampleclient computing platform 104 including entity visuals 412 regardingoffers with pre-approved and/or activated functionality according to anexample embodiment. The interface 400 on a display of a client computingplatform 104 includes an entity information 404, an entity name 406, ajoin button 408, and a Login button 410. In some embodiments, the join408 provides access to join a platform (e.g., a payment platform) forone or more accounts of the entity associated with the client computingplatform 104. In some implementations, the Login button 410 providesaccess to the platform that has already been joined.

In some implementations, a graphic is generated based on any receivedoffers for joining a payment platform. The graphic may include visualindications such as logos 412 or other identifiable visuals related toone or more entities. In some implementations, the logos or otheridentifiable visuals may be adjusted regarding size, color, prominenceon the screen, and other visual indications that may represent astrength of a connection between the respective entity associated withthe client computing platform 104 and the one or more entitiesassociated with the identifiable visuals that are already members of theplatform. Other visuals may be displayed indicating advantages andincentives to joining the platform. In some implementations visualsindicating advantages and incentives to joining the platform mayindicate which connections to the one or more entities that are alreadymembers of the platform would benefit.

In some implementations, visuals may include pop-up alerts providingmore information on incentives offered to join or advantages to joiningthe platform. In some implementations, a user of the client computingplatform 104 can click on the alert to obtain more information on theterms of the offer and/or any advantages and efficiencies in joining.Other visual indicators may include specific information display forvarious entities displayed as well as more detail on how transactionsbetween one or more of the entities could be simplified upon joining theplatform. In some implementations, the offer can be immediately acceptedby using a Join button 408.

The embodiments described herein have been described with reference todrawings. The drawings illustrate certain details of specificembodiments that implement the systems, methods, and programs describedherein. However, describing the embodiments with drawings should not beconstrued as imposing on the disclosure any limitations that may bepresent in the drawings.

It should be understood that no claim element herein is to be construedunder the provisions of 35 U.S.C. § 112(f), unless the element isexpressly recited using the phrase “means for.”

As used herein, the term “circuit” may include hardware structured toexecute the functions described herein. In some embodiments, eachrespective “circuit” may include machine-readable media for configuringthe hardware to execute the functions described herein. The circuit maybe embodied as one or more circuitry components including, but notlimited to, processing circuitry, network circuits, peripheral devices,input devices, output devices, and sensors. In some embodiments, acircuit may take the form of one or more analog circuits, electroniccircuits (e.g., integrated circuits (IC), discrete circuits, system on achip (SOCs) circuits), telecommunication circuits, hybrid circuits, andany other type of “circuit.” In this regard, the “circuit” may includeany type of component for accomplishing or facilitating achievement ofthe operations described herein. For example, a circuit as describedherein may include one or more transistors, logic gates (e.g., NAND,AND, NOR, OR, XOR, NOT, XNOR), resistors, multiplexers, registers,capacitors, inductors, diodes, wiring, and so on).

The “circuit” may also include one or more processors communicativelycoupled to one or more memory or memory devices. In this regard, the oneor more processors may execute instructions stored in the memory or mayexecute instructions otherwise accessible to the one or more processors.In some embodiments, the one or more processors may be embodied invarious ways. The one or more processors may be constructed in a mannersufficient to perform at least the operations described herein. In someembodiments, the one or more processors may be shared by multiplecircuits (e.g., circuit A and circuit B may comprise or otherwise sharethe same processor which, in some example embodiments, may executeinstructions stored, or otherwise accessed, via different areas ofmemory). Alternatively or additionally, the one or more processors maybe structured to perform or otherwise execute certain operationsindependent of one or more co-processors. In other example embodiments,two or more processors may be coupled via a bus to enable independent,parallel, pipelined, or multi-threaded instruction execution. Eachprocessor may be implemented as one or more general-purpose processors,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), digital signal processors (DSPs), or other suitableelectronic data processing components structured to execute instructionsprovided by memory. The one or more processors may take the form of asingle core processor, multi-core processor (e.g., a dual coreprocessor, triple core processor, quad core processor), microprocessor,etc. In some embodiments, the one or more processors may be external tothe apparatus, for example the one or more processors may be a remoteprocessor (e.g., a cloud based processor). Alternatively oradditionally, the one or more processors may be internal and/or local tothe apparatus. In this regard, a given circuit or components thereof maybe disposed locally (e.g., as part of a local server, a local computingsystem) or remotely (e.g., as part of a remote server such as a cloudbased server). To that end, a “circuit” as described herein may includecomponents that are distributed across one or more locations.

An exemplary system for implementing the overall system or portions ofthe embodiments might include general purpose computing devices in theform of computers, including a processing unit, a system memory, and asystem bus that couples various system components including the systemmemory to the processing unit. Each memory device may includenon-transient volatile storage media, non-volatile storage media,non-transitory storage media (e.g., one or more volatile and/ornon-volatile memories), etc. In some embodiments, the non-volatile mediamay take the form of ROM, flash memory (e.g., flash memory such as NAND,3D NAND, NOR, 3D NOR), EEPROM, MRAM, magnetic storage, hard discs,optical discs, etc. In other embodiments, the volatile storage media maytake the form of RAM, TRAM, ZRAM, etc. Combinations of the above arealso included within the scope of machine-readable media. In thisregard, machine-executable instructions comprise, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions. Each respective memory devicemay be operable to maintain or otherwise store information relating tothe operations performed by one or more associated circuits, includingprocessor instructions and related data (e.g., database components,object code components, script components, etc.), in accordance with theexample embodiments described herein.

It should also be noted that the term “input device,” as describedherein, may include any type of input device or input devices including,but not limited to, a keyboard, a keypad, a mouse, joystick, or otherinput devices capable of performing a similar function. Comparatively,the term “output device,” as described herein, may include any type ofoutput device or output devices including, but not limited to, acomputer monitor, printer, facsimile machine, or other output devicescapable of performing a similar function.

Any foregoing references to currency or funds are intended to includefiat currencies, non-fiat currencies (e.g., precious metals), andmath-based currencies (often referred to as cryptocurrencies). Examplesof math-based currencies include Bitcoin, Litecoin, Dogecoin, and thelike.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure as defined in the appended claims.Such variations will depend on the machine-readable media and hardwaresystems chosen and on designer choice. It is understood that all suchvariations are within the scope of the disclosure. Likewise, softwareand web implementations of the present disclosure could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various database searching steps, correlationsteps, comparison steps, and decision steps.

The foregoing description of embodiments has been presented for purposesof illustration and description. It is not intended to be exhaustive orto limit the disclosure to the precise form disclosed, and modificationsand variations are possible in light of the above teachings or may beacquired from this disclosure. The embodiments were chosen and describedto explain the principals of the disclosure and its practicalapplication to enable one skilled in the art to utilize the variousembodiments and with various modifications as are suited to theparticular use contemplated. Other substitutions, modifications,changes, and omissions may be made in the design, operating conditions,and arrangement of the embodiments without departing from the scope ofthe present disclosure as expressed in the appended claims.

What is claimed is:
 1. A system configured for pre-approving onboardingto a payment platform, executing on a processing device, the systemcomprising: one or more hardware processors configured bymachine-readable instructions to: access a node network, wherein aplurality of nodes of the node network comprise data associated with aplurality of business entities, and wherein strength of connectionsbetween nodes are weighted according to a number of transactions betweenthe respective associated business entities; determine a first businessentity associated with a first node of the plurality of nodes is not amember of a payment platform; determine a total strength of connectionsof the first node to one or more nodes of the plurality of nodes exceedsa predetermined threshold value, wherein the respective associatedbusiness entities of the one or more nodes are members of the paymentplatform; flag the first node of the plurality of nodes for an offer ofonboarding to the payment platform consequent to determining the totalstrength of connections of the first node to the one or more nodes ofthe plurality of nodes exceeds the predetermined threshold value;determine a data field required for a pre-approval of a firstfunctionality of the payment platform for the first business entity isincomplete; access a permissioned blockchain of the payment platformcontaining transaction information associated with the plurality ofbusiness entities in order to: analyze a transaction history associatedwith the first business entity; and analyze a transaction volume of thefirst business entity, the analysis including a comparison to othermembers of the payment platform; determine a first data to populate therequired data field, the determination based at least in part on theanalyses of the first business entity completed on the permissionedblockchain; select a first parameter for inclusion in the offer, whereinthe first parameter is associated with an incentive for the firstfunctionality of the payment platform, wherein the first parameter isselected based at least in part on the analyses of the first businessentity completed on the permissioned blockchain and on a plurality oftransactions predicted to occur subsequent to the first business entityaccepting the offer; preapprove the first functionality of the paymentplatform based on the analyses of the first business entity completed onthe permissioned blockchain and on the plurality of transactionspredicted to occur subsequent to the first business entity accepting theoffer; include the first functionality of the payment platform in theoffer subsequent to preapproving the first functionality of the paymentplatform; display a visual indication on a screen of a device associatedwith the first business entity corresponding to the offer, wherein thevisual indication comprises logos or other identifiable visuals relatedto the respective associated business entities of the one or more nodesthat are already members of the payment platform, wherein the size,color, or prominence on the screen of the visual indication depicts astrength of a connection between the first business entity and therespective associated business entities of the one or more nodes thatare already members of the payment platform; receive an acceptance tothe offer from the device associated with the first business entity; andjoin the first business entity to the payment platform.
 2. The system ofclaim 1, wherein analyzing the transaction history comprises determininga value of a parameter associated with the transaction history exceeds asecond predetermined threshold value.
 3. The system of claim 1, whereinjoining the first business entity to the payment platform comprisescreating an account on the payment platform, a configuration of thecreated account based on including the first functionality of thepayment platform in the offer; and wherein joining the first businessentity to the payment platform comprises associating the first node withthe created account.
 4. The system of claim 1, wherein the one or morehardware processors are further configured by machine-readableinstructions to: identify a second functionality of the payment platformnot available to the first business entity subsequent to joining thefirst business entity to the payment platform; send a request for firstdata associated with the second functionality to the device associatedwith the first business entity; receive the first data from the deviceassociated with the first business entity; and update the account of thepayment platform to add the second functionality.
 5. The system of claim1, wherein the offer includes data comprising advantages or incentivesassociated with joining the payment platform.
 6. The system of claim 5,wherein the data comprising advantages or incentives associated withjoining the payment platform further comprises graphical data that, whendisplayed on the device associated with the first business entity,illustrates the advantages or incentives associated with joining thepayment platform, the illustrated advantages or incentives structured toshow which connections to the respective associated business entitiesprovide a benefit to the first business entity upon joining, therespective associated business entities associated with the one or morenodes that are already members of the payment platform.
 7. The system ofclaim 1, wherein the one or more hardware processors are furtherconfigured by machine-readable instructions to: receive data comprisinga first transaction with a second business entity; determine the secondbusiness entity does not have an associated node in the node network;and create a new node in the node network associated with the secondbusiness entity.
 8. The system of claim 7, wherein the one or morehardware processors are further configured by machine-readableinstructions to: receive data comprising a second transaction with thesecond business entity; and update a weight of a connection between thefirst business entity and the second business entity consequent toreceiving the data comprising the second transaction.
 9. A method ofpre-approving onboarding to a payment platform, executing on aprocessing device, comprising: accessing a node network, wherein aplurality of nodes of the node network comprise data associated with aplurality of business entities, and wherein strength of connectionsbetween nodes are weighted according to a number of transactions betweenthe respective associated business entities; determining a firstbusiness entity associated with a first node of the plurality of nodesis not a member of a payment platform; determining a total strength ofconnections of the first node to one or more nodes of the plurality ofnodes exceeds a predetermined threshold value, wherein the respectiveassociated business entities of the one or more nodes are members of thepayment platform; flagging the first node of the plurality of nodes foran offer of onboarding to the payment platform consequent to determiningthe total strength of connections of the first node to the one or morenodes of the plurality of nodes exceeds the predetermined thresholdvalue; determining a data field required for a pre-approval of a firstfunctionality of the payment platform for the first business entity isincomplete; accessing a permissioned blockchain of the payment platformcontaining transaction information associated with the plurality ofbusiness entities in order to: analyze a transaction history associatedwith the first business entity; and analyze a transaction volume of thefirst business entity, the analysis including a comparison to othermembers of the payment platform; determining a first data to populatethe required data field, the determination based at least in part on theanalyses of the first business entity completed on the permissionedblockchain; selecting a first parameter for inclusion in the offer,wherein the first parameter is associated with an incentive for thefirst functionality of the payment platform, wherein the first parameteris selected based at least in part on the analyses of the first businessentity completed on the permissioned blockchain and on a plurality oftransactions predicted to occur subsequent to the first business entityaccepting the offer; preapproving the first functionality of the paymentplatform based on the analyses of the first business entity completed onthe permissioned blockchain and on the plurality of transactionspredicted to occur subsequent to the first business entity accepting theoffer; including the first functionality of the payment platform in theoffer subsequent to preapproving the first functionality of the paymentplatform; displaying a visual indication corresponding to the offer on ascreen of a device associated with the first business entity, whereinthe visual indication comprises logos or other identifiable visualsrelated to the respective associated business entities of the one ormore nodes that are already members of the payment platform, wherein thesize, color, or prominence on the screen of the visual indicationdepicts a strength of a connection between the first business entity andthe respective associated business entities of the one or more nodesthat are already members of the payment platform; receiving anacceptance to the offer from the device associated with the firstbusiness entity; and joining the first business entity to the paymentplatform.
 10. The method of claim 9, wherein analyzing the transactionhistory comprises determining a value of a parameter associated with thetransaction history exceeds a second predetermined threshold value. 11.The method of claim 9, wherein joining the first business entity to thepayment platform comprises creating an account on the payment platform,a configuration of the created account based on including the firstfunctionality of the payment platform in the offer; and wherein joiningthe first business entity to the payment platform comprises associatingthe first node with the created account.
 12. The method of claim 9,further comprising: identifying a second functionality of the paymentplatform not available to the first business entity subsequent tojoining the first business entity to the payment platform; sending arequest for first data associated with the second functionality to thedevice associated with the first business entity; receiving the firstdata from the device associated with the first business entity; andupdating the account of the payment platform to add the secondfunctionality.
 13. The method of claim 9, wherein the offer includesdata comprising advantages or incentives associated with joining thepayment platform.
 14. The method of claim 13, wherein the datacomprising advantages or incentives associated with joining the paymentplatform further comprises graphical data that, when displayed on thedevice associated with the first business entity, illustrates theadvantages or incentives associated with joining the payment platform,the illustrated advantages or incentives structured to show whichconnections to the respective associated business entities would providea benefit to the first business entity upon joining, the respectiveassociated business entities associated with the one or more nodes thatare already members of the payment platform.
 15. The method of claim 9,further comprising: receiving data comprising a first transaction with asecond business entity; determining the second business entity does nothave an associated node in the node network; and creating a new node inthe node network associated with the second business entity.
 16. Themethod of claim 15, further comprising: receiving data comprising asecond transaction with the second business entity; and updating aweight of a connection between the first business entity and the secondbusiness entity consequent to receiving the data comprising the secondtransaction.
 17. A non-transient computer-readable storage medium havinginstructions embodied thereon, the instructions being executable by oneor more processors to perform a method for pre-approving onboarding to apayment platform, executing on a processing device, the methodcomprising: accessing a node network, wherein a plurality of nodes ofthe node network comprise data associated with a plurality of businessentities, and wherein strength of connections between nodes are weightedaccording to a number of transactions between the respective associatedbusiness entities; determining a first business entity associated with afirst node of the plurality of nodes is not a member of a paymentplatform; determining a total strength of connections of the first nodeto one or more nodes of the plurality of nodes exceeds a predeterminedthreshold value, wherein the respective associated business entities ofthe one or more nodes are members of the payment platform; flagging thefirst node of the plurality of nodes for an offer of onboarding to thepayment platform consequent to determining the total strength ofconnections of the first node to the one or more nodes of the pluralityof nodes exceeds the predetermined threshold value; determining a datafield required for a pre-approval of a first functionality of thepayment platform for the first business entity is incomplete; accessinga permissioned blockchain of the payment platform containing transactioninformation associated with the plurality of business entities in orderto: analyze a transaction history associated with the first businessentity; and analyze a transaction volume of the first business entity,the analysis including a comparison to other members of the paymentplatform; determining a first data to populate the required data field,the determination based at least in part on the analyses of the firstbusiness entity completed on the permissioned blockchain; selecting afirst parameter for inclusion in the offer, wherein the first parameteris associated with an incentive for the first functionality of thepayment platform, wherein the first parameter is selected based at leastin part on the analyses of the first business entity completed on thepermissioned blockchain and on a plurality of transactions predicted tooccur subsequent to the first business entity accepting the offer;preapproving the first functionality of the payment platform based onthe analyses of the first business entity completed on the permissionedblockchain and on the plurality of transactions predicted to occursubsequent to the first business entity accepting the offer; includingthe first functionality of the payment platform in the offer subsequentto preapproving the first functionality of the payment platform;displaying a visual indication corresponding to the offer on a screen ofa device associated with the first business entity, wherein the visualindication comprises logos or other identifiable visuals related to therespective associated business entities of the one or more nodes thatare already members of the payment platform, wherein the size, color, orprominence on the screen of the visual indication depicts a strength ofa connection between the first business entity and the respectiveassociated business entities of the one or more nodes that are alreadymembers of the payment platform; receiving an acceptance to the offerfrom the device associated with the first business entity; and joiningthe first business entity to the payment platform.
 18. Thecomputer-readable storage medium of claim 17, wherein analyzing thetransaction history comprises determining a value of a parameterassociated with the transaction history exceeds a second predeterminedthreshold value.
 19. The computer-readable storage medium of claim 17,wherein joining the first business entity to the payment platformcomprises creating an account on the payment platform, a configurationof the created account based on including the first functionality of thepayment platform in the offer; and wherein joining the first businessentity to the payment platform comprises associating the first node withthe created account.
 20. The computer-readable storage medium of claim17, wherein the method further comprises: identifying a secondfunctionality of the payment platform not available to the firstbusiness entity subsequent to joining the first business entity to thepayment platform; sending a request for first data associated with thesecond functionality to the device associated with the first businessentity; receiving the first data from the device associated with thefirst business entity; and updating the account of the payment platformto add the second functionality.
 21. The computer-readable storagemedium of claim 17, wherein the offer includes data comprisingadvantages or incentives associated with joining the platform.
 22. Thecomputer-readable storage medium of claim 21, wherein the datacomprising advantages or incentives associated with joining the platformfurther comprises graphical data that, when displayed on the deviceassociated with the first business entity, illustrates the advantages orincentives associated with joining the platform, the illustratedadvantages or incentives structured to show which connections to therespective associated business entities would provide a benefit to thefirst business entity upon joining, the respective associated businessentities associated with the one or more nodes that are already membersof the payment platform.
 23. The computer-readable storage medium ofclaim 17, wherein the method further comprises: receiving datacomprising a first transaction with a second business entity;determining the second business entity does not have an associated nodein the node network; and creating a new node in the node networkassociated with the second business entity.
 24. The computer-readablestorage medium of claim 23, wherein the method further comprises:receiving data comprising a second transaction with the second businessentity; and updating a weight of a connection between the first businessentity and the second business entity consequent to receiving the datacomprising the second transaction.